Fixes #80

Problem:
The useRemoteConnection hook stored the WebSocket instance using useState. The useEffect cleanup function captured the initial state value (null) via closure, so ws?.close() on unmount never actually closed the real socket. This caused:

• Zombie WebSocket connections that stayed open after navigating away
• Pending reconnect timers firing after the component was gone
• WebSocket is closed before the connection is established browser warnings during navigation (React Strict Mode double-mounting)
  Fix useRemoteConnection.ts :

1. Replaced useState<WebSocket> with useRef<WebSocket> so cleanup always accesses the current socket
2. Added an isMounted flag to prevent reconnection attempts after unmount
3. Deferred initial socket creation with setTimeout(connect, 0) to avoid creating sockets during React Strict Mode's instant unmount cycle
4. Nullified event handlers (onopen, onclose, onerror before calling .close() to prevent cascading error events
5. Stabilized send and sendCombo callbacks with empty dependency arrays since ref identity never changes

Checklist

• My PR addresses a single issue, fixes a single bug or makes a single improvement.
• My code follows the project's code style and conventions
• If applicable, I have made corresponding changes or additions to the documentation
• If applicable, I have made corresponding changes or additions to tests
• My changes generate no new warnings or errors
• I have joined the Discord server and I will share a link to this PR with the project maintainers there
• I have read the Contribution Guidelines
• Once I submit my PR, CodeRabbit AI will automatically review it and I will address CodeRabbit's comments.